Add Turborepo monorepo configuration with pnpm workspaces by gregnazario · Pull Request #862 · aptos-labs/aptos-ts-sdk

gregnazario · 2026-03-21T04:59:09Z

Description

Sets up Turborepo for monorepo orchestration so that multiple apps and packages can be easily organized in this repository.

What's included:

turbo.json — Task pipeline configuration for build, test, lint, check, fmt, and dev tasks. Root tasks use the //#task syntax with scoped inputs for efficient caching. Workspace package builds depend on ^build plus the root SDK build (//#build) to ensure correct ordering.
pnpm-workspace.yaml — Workspace package definitions covering packages/*, apps/*, confidential-assets, examples/*, and projects/*.
packages/ and apps/ directories — Scaffolded with .gitkeep for adding new workspace packages and applications.
Workspace-wide turbo scripts — build:all, test:all, lint:all, check:all, fmt:all added to root package.json (filtered to core packages only).
All sub-packages wired as workspace members — confidential-assets, examples/*, and projects/* use workspace:* protocol for the @aptos-labs/ts-sdk dependency; pnpm overrides consolidated at root; all stale nested lockfiles removed.
CI updated — run-confidential-assets-tests action now builds the root SDK before running tests (required since workspace:* resolves to the local unbuilt root instead of the pre-built npm package). Playwright browser download skipped in this CI job.
Confidential-assets test funding fix — Increased test account funding from 1 APT to 10 APT to prevent INSUFFICIENT_BALANCE_FOR_TRANSACTION_FEE failures after the default maxGasAmount increase to 2,000,000.
.turbo added to .gitignore
Documentation updated — AGENTS.md, CLAUDE.md, and CHANGELOG.md updated with monorepo structure and new commands.

All existing SDK commands (pnpm build, pnpm test, pnpm check, etc.) continue to work unchanged.

Test Plan

pnpm install correctly resolves all workspace dependencies (9 workspace projects)
turbo run build --dry shows correct dependency ordering (//#build → dependent packages)
pnpm build:all succeeds: root SDK and confidential-assets build (2 successful, examples/projects excluded via filter)
pnpm build still works standalone for the SDK
pnpm check:all runs biome checks across core workspace packages
pnpm check passes (242 files, no issues)
Playwright binary is correctly accessible in examples/web-test/node_modules/.bin/ after workspace install
CI: bun, deno, web/browser, unit+e2e, examples, confidential-assets tests all pass

Review feedback addressed

Removed all stale nested lockfiles (pnpm-lock.yaml in examples/*, projects/gas-station, and bun.lock in examples/bun-test)
Moved @aptos-labs/ts-sdk from devDependencies to dependencies in projects/gas-station since it's imported at runtime
Removed redundant peerDependencies from projects/gas-station (it's a demo app, not a published library)
Increased confidential-assets test funding from 1 APT to 10 APT to fix INSUFFICIENT_BALANCE_FOR_TRANSACTION_FEE
Added PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1 to confidential-assets CI install step to avoid unnecessary browser downloads
Removed ./confidential-assets from lint:all/check:all/fmt:all filters (that package has no lint/check/fmt scripts)
Removed private key and decryption key console.log statements from negativeTransfer, negativeWithdraw, and negativeNormalize test files to avoid leaking keys in CI logs; cleaned up unused imports
Re: turbo.json //#build and //#test etc. — these are correct Turborepo v2 root task definitions; //#build maps to the root package.json's build script, and the //#test///#lint/etc. configure caching inputs when those tasks are run on the root package via {.} filter

Checklist

Have you ran pnpm fmt?
Have you updated the CHANGELOG.md?

Copilot

Pull request overview

This PR introduces a Turborepo + pnpm-workspaces monorepo setup for the Aptos TypeScript SDK repo, enabling orchestrated build/test/lint/check/fmt workflows across the root SDK and additional workspace members.

Changes:

Add turbo.json task pipeline config and pnpm-workspace.yaml workspace definitions.
Wire workspace members to depend on the root SDK via workspace:* and consolidate pnpm overrides at the root.
Add repo-wide *:all scripts and update docs/changelog + ignore .turbo.

Reviewed changes

Copilot reviewed 15 out of 20 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
turbo.json	Defines Turborepo task graph (build/test/lint/check/fmt/dev) and root-task inputs/outputs.
pnpm-workspace.yaml	Declares workspace package globs for packages/apps/examples/projects/confidential-assets.
package.json	Adds turbo + `build:all`/`test:all`/`lint:all`/`check:all`/`fmt:all` scripts; consolidates pnpm overrides.
confidential-assets/package.json	Adds `@aptos-labs/ts-sdk` as `workspace:*` devDependency; removes per-package pnpm overrides.
projects/gas-station/package.json	Switches to `workspace:*` for the SDK and removes per-package pnpm overrides.
examples/web-test/package.json	Switches SDK dependency from link to `workspace:*`.
examples/typescript/package.json	Switches SDK dependency from link to `workspace:*`.
examples/typescript-esm/package.json	Switches SDK dependency from link to `workspace:*`.
examples/javascript/package.json	Switches SDK dependency from link to `workspace:*`.
examples/deno-test/package.json	Switches SDK dependency from file to `workspace:*`.
examples/bun-test/package.json	Switches SDK dependency from file to `workspace:*`.
confidential-assets/pnpm-lock.yaml	Removes nested lockfile in favor of the workspace root lockfile.
.gitignore	Ignores Turborepo state directory (`.turbo`).
AGENTS.md	Documents new monorepo layout and turbo commands.
CLAUDE.md	Documents new monorepo structure and turbo commands.
CHANGELOG.md	Adds entries describing the monorepo/turbo setup.
packages/.gitkeep	Scaffolds `packages/` directory.
apps/.gitkeep	Scaffolds `apps/` directory.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-21T05:15:30Z

projects/gas-station/package.json

  "devDependencies": {
+    "@aptos-labs/ts-sdk": "workspace:*",
    "@types/express": "^5.0.6",
    "@types/node": "^22.19.13",
    "tsx": "^4.21.0",
    "tsup": "^8.5.1",
    "typescript": "^5.9.3"
  },
  "peerDependencies": {
    "@aptos-labs/ts-sdk": "^5.2.1 || ^6.1.0"
-  },
-  "pnpm": {
-    "overrides": {
-      "minimatch@^9": "^9.0.7",
-      "qs@^6": "^6.14.1",
-      "glob@^10": "^10.5.0",
-      "rollup@^4": "^4.59.0"
-    }
  }


@aptos-labs/ts-sdk is imported at runtime by this project (e.g. in src/server.ts), so it should be listed under dependencies rather than devDependencies. Keeping it as a devDependency can break production installs that omit devDependencies.

Copilot · 2026-03-21T05:15:30Z

projects/gas-station/package.json

    "express": "^5.2.1"
  },
  "devDependencies": {
+    "@aptos-labs/ts-sdk": "workspace:*",
    "@types/express": "^5.0.6",
    "@types/node": "^22.19.13",
    "tsx": "^4.21.0",
    "tsup": "^8.5.1",
    "typescript": "^5.9.3"
  },
  "peerDependencies": {
    "@aptos-labs/ts-sdk": "^5.2.1 || ^6.1.0"
-  },
-  "pnpm": {
-    "overrides": {
-      "minimatch@^9": "^9.0.7",
-      "qs@^6": "^6.14.1",
-      "glob@^10": "^10.5.0",
-      "rollup@^4": "^4.59.0"
-    }
  }


Now that this project is a pnpm workspace member and uses workspace:*, the existing projects/gas-station/pnpm-lock.yaml is stale (it still pins @aptos-labs/ts-sdk differently). Consider removing the nested lockfile and relying on the workspace root pnpm-lock.yaml to avoid confusion and accidental drift.

Copilot · 2026-03-21T05:15:30Z

examples/web-test/package.json

  },
  "dependencies": {
-    "@aptos-labs/ts-sdk": "link:../.."
+    "@aptos-labs/ts-sdk": "workspace:*"


This package now depends on @aptos-labs/ts-sdk via workspace:*, but examples/web-test/pnpm-lock.yaml still references the old link:../.. specifier. In a workspace setup, it’s better to remove the per-package lockfile (and rely on the root pnpm-lock.yaml) or regenerate it to match the new dependency spec.

Suggested change

"@aptos-labs/ts-sdk": "workspace:*"

"@aptos-labs/ts-sdk": "link:../.."

Copilot · 2026-03-21T05:15:31Z

examples/typescript/package.json

  "author": "",
  "dependencies": {
-    "@aptos-labs/ts-sdk": "link:../..",
+    "@aptos-labs/ts-sdk": "workspace:*",


This package now depends on @aptos-labs/ts-sdk via workspace:*, but examples/typescript/pnpm-lock.yaml still references the old link:../.. specifier. In a workspace setup, it’s better to remove the per-package lockfile (and rely on the root pnpm-lock.yaml) or regenerate it to match the new dependency spec.

Suggested change

"@aptos-labs/ts-sdk": "workspace:*",

"@aptos-labs/ts-sdk": "link:../..",

Copilot · 2026-03-21T05:15:31Z

examples/typescript-esm/package.json

  "keywords": [],
  "author": "",
  "dependencies": {
-    "@aptos-labs/ts-sdk": "link:../..",
+    "@aptos-labs/ts-sdk": "workspace:*",
    "@noble/hashes": "^1.7.2",
    "dotenv": "17.3.1",


This package now depends on @aptos-labs/ts-sdk via workspace:*, but examples/typescript-esm/pnpm-lock.yaml still references the old link:../.. specifier. In a workspace setup, it’s better to remove the per-package lockfile (and rely on the root pnpm-lock.yaml) or regenerate it to match the new dependency spec.

Copilot · 2026-03-21T05:15:31Z

examples/javascript/package.json

  "keywords": [],
  "author": "",
  "dependencies": {
-    "@aptos-labs/ts-sdk": "link:../..",
+    "@aptos-labs/ts-sdk": "workspace:*",
    "npm-run-all2": "8.0.4"
  }


This package now depends on @aptos-labs/ts-sdk via workspace:*, but examples/javascript/pnpm-lock.yaml still references the old link:../.. specifier. In a workspace setup, it’s better to remove the per-package lockfile (and rely on the root pnpm-lock.yaml) or regenerate it to match the new dependency spec.

Copilot · 2026-03-21T05:15:31Z

examples/bun-test/package.json

  },
  "dependencies": {
-    "@aptos-labs/ts-sdk": "file:../.."
+    "@aptos-labs/ts-sdk": "workspace:*"


This package now depends on @aptos-labs/ts-sdk via workspace:*, but examples/bun-test/bun.lock still pins @aptos-labs/ts-sdk as file:../... Either update/regenerate the Bun lockfile to match the new specifier, or consider removing it if pnpm is the source of truth for installs in this monorepo.

Suggested change

"@aptos-labs/ts-sdk": "workspace:*"

"@aptos-labs/ts-sdk": "file:../.."

Copilot

Pull request overview

Copilot reviewed 21 out of 32 changed files in this pull request and generated 2 comments.

Files not reviewed (5)

examples/javascript/pnpm-lock.yaml: Language not supported
examples/typescript-esm/pnpm-lock.yaml: Language not supported
examples/typescript/pnpm-lock.yaml: Language not supported
examples/web-test/pnpm-lock.yaml: Language not supported
projects/gas-station/pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-21T05:40:06Z

turbo.json

+    "build": {
+      "dependsOn": ["^build", "//#build"],
+      "outputs": ["dist/**"]
+    },
+    "//#build": {
+      "inputs": ["src/**", "tsup.config.ts", "tsconfig.json", "package.json"],
+      "outputs": ["dist/**"]


build.dependsOn references "//#build", but no workspace package defines a //#build script (root package.json only has build, not //#build). This makes the task graph inconsistent and can cause turbo run build/pnpm build:all to fail or silently skip the intended root build step. Either remove "//#build" and rely on ^build (since workspace deps already enforce ordering), or add corresponding //#build (and other //#*) scripts in the root package.json and wire test/lint/check to depend on them as intended.

projects/gas-station/package.json

- Add turbo.json with task pipeline configuration for build, test, lint, check, fmt, and dev tasks - Add pnpm-workspace.yaml defining workspace packages (packages/*, apps/*, confidential-assets) - Create packages/ and apps/ directories for organizing new workspace packages and applications - Install turbo ^2.8.20 as a devDependency - Add workspace-wide turbo scripts: build:all, test:all, lint:all, check:all, fmt:all - Wire up confidential-assets as a workspace member using workspace:* protocol - Merge confidential-assets pnpm overrides into root package.json (workspace-level only) - Remove confidential-assets separate pnpm-lock.yaml (now managed by root workspace install) - Add .turbo to .gitignore - Add onlyBuiltDependencies for @swc/core and esbuild - Update AGENTS.md and CLAUDE.md with monorepo structure and turbo commands - Update CHANGELOG.md with Turborepo setup entry Co-authored-by: Greg Nazario <greg@gnazar.io>

- Add examples/* and projects/* to pnpm-workspace.yaml so pnpm install correctly resolves their dependencies (fixes run-web-tests CI failure where playwright was not found after workspace detection) - Update all example/project SDK dependencies from link:../.. or file:../.. to workspace:* protocol - Merge projects/gas-station pnpm overrides into root package.json - Filter turbo workspace scripts (build:all, test:all, etc.) to only run on core packages (root SDK, packages/*, confidential-assets), excluding examples and projects which have standalone build/test workflows - Update AGENTS.md and CLAUDE.md documentation Co-authored-by: Greg Nazario <greg@gnazar.io>

The confidential-assets tests now resolve @aptos-labs/ts-sdk via workspace:* which points to the local root package. Vite needs the built dist/ to resolve the entry point. Previously this worked because the separate pnpm install pulled the pre-built package from npm. - Replace redundant 'cd confidential-assets && pnpm install' with 'pnpm build' - Root pnpm install already handles workspace member dependencies Co-authored-by: Greg Nazario <greg@gnazar.io>

Now that all sub-packages are pnpm workspace members, the root pnpm-lock.yaml is the single source of truth for dependency resolution. Remove the per-package lockfiles that referenced the old link:/file: specifiers. Co-authored-by: Greg Nazario <greg@gnazar.io>

The SDK is imported at runtime in server.ts and client.ts, so it belongs in dependencies rather than devDependencies to avoid breaking production installs that omit devDependencies. Co-authored-by: Greg Nazario <greg@gnazar.io>

The default maxGasAmount was increased to 2,000,000 in SDK 6.2.0, which at 100 octas/gas reserves 2 APT for fees. The tests were funding accounts with only 1 APT (100,000,000 octas), causing INSUFFICIENT_BALANCE_FOR_ TRANSACTION_FEE errors. Increase to 10 APT (1,000,000,000 octas) to match the main SDK test conventions. Co-authored-by: Greg Nazario <greg@gnazar.io>

gas-station is a demo app, not a published library. The SDK is already in dependencies via workspace:*, so the peerDependencies entry is unnecessary and would only trigger warnings. Co-authored-by: Greg Nazario <greg@gnazar.io>

Copilot

Pull request overview

Copilot reviewed 21 out of 32 changed files in this pull request and generated 2 comments.

Files not reviewed (5)

examples/javascript/pnpm-lock.yaml: Language not supported
examples/typescript-esm/pnpm-lock.yaml: Language not supported
examples/typescript/pnpm-lock.yaml: Language not supported
examples/web-test/pnpm-lock.yaml: Language not supported
projects/gas-station/pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-23T21:30:03Z

.github/actions/run-confidential-assets-tests/action.yaml

+    # Run package install for all workspace members.
    - run: pnpm install --frozen-lockfile
      shell: bash

-    # Install the dependencies for the Confidential Assets tests
-    - run: cd confidential-assets && pnpm install --frozen-lockfile
+    # Build the root SDK so confidential-assets can resolve @aptos-labs/ts-sdk.
+    - run: pnpm build
      shell: bash


pnpm install at the repo root will now install dependencies for all workspace members (including examples/web-test which depends on @playwright/test). That can trigger Playwright’s large browser downloads during install and significantly slow or destabilize this CI job even though the job only runs confidential-assets tests. Consider filtering the install to just the root + confidential-assets workspaces, or setting PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1 for this job’s install step.

Copilot · 2026-03-23T21:30:03Z

package.json

+    "lint:all": "turbo run lint --filter='./packages/*' --filter='./confidential-assets' --filter='{.}'",
+    "check:all": "turbo run check --filter='./packages/*' --filter='./confidential-assets' --filter='{.}'",
+    "fmt:all": "turbo run fmt --filter='./packages/*' --filter='./confidential-assets' --filter='{.}'"


The new lint:all / check:all / fmt:all scripts include ./confidential-assets, but confidential-assets/package.json does not define lint, check, or fmt scripts. turbo run lint|check|fmt will fail for that workspace unless those scripts are added (and the needed tooling deps), or the filters are adjusted to exclude confidential-assets from these commands.

Suggested change

"lint:all": "turbo run lint --filter='./packages/*' --filter='./confidential-assets' --filter='{.}'",

"check:all": "turbo run check --filter='./packages/*' --filter='./confidential-assets' --filter='{.}'",

"fmt:all": "turbo run fmt --filter='./packages/*' --filter='./confidential-assets' --filter='{.}'"

"lint:all": "turbo run lint --filter='./packages/*' --filter='{.}'",

"check:all": "turbo run check --filter='./packages/*' --filter='{.}'",

"fmt:all": "turbo run fmt --filter='./packages/*' --filter='{.}'"

Copilot

Pull request overview

Copilot reviewed 21 out of 32 changed files in this pull request and generated 3 comments.

Files not reviewed (5)

examples/javascript/pnpm-lock.yaml: Language not supported
examples/typescript-esm/pnpm-lock.yaml: Language not supported
examples/typescript/pnpm-lock.yaml: Language not supported
examples/web-test/pnpm-lock.yaml: Language not supported
projects/gas-station/pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (1)

confidential-assets/tests/units/api/negativeNormalize.test.ts:26

These tests log alice.privateKey/decryption keys to stdout. In CI this ends up in build logs, which is sensitive even for test accounts and makes it easy to accidentally leak real keys if the helper setup changes. Please remove these logs or gate them behind an explicit debug env flag.

  console.log("pk", alice.privateKey.toString());
  console.log("dk", aliceConfidential.toString());
  console.log("ek", aliceConfidential.publicKey().toString());

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-23T21:59:27Z

turbo.json

+    "test": {
+      "dependsOn": ["^build"]
+    },
+    "//#test": {
+      "inputs": ["src/**", "tests/**", "vitest.config.ts", "tsconfig.json", "package.json"],
+      "dependsOn": ["//#build"]
+    },
+    "lint": {},
+    "//#lint": {
+      "inputs": ["src/**", "tests/**", "biome.json"]
+    },
+    "check": {},
+    "//#check": {
+      "inputs": ["src/**", "tests/**", "biome.json"]
+    },
+    "fmt": {
+      "cache": false
+    },
+    "//#fmt": {
+      "cache": false
+    },


The //#test, //#lint, //#check, and //#fmt tasks define scoped inputs/settings, but nothing in this config references them (e.g., test doesn’t depend on //#test, lint doesn’t depend on //#lint, etc.). As written, these root-task definitions will never run and their input scoping won’t affect caching. Either wire them into the corresponding tasks (or update the main tasks to include the intended inputs), or remove them to avoid confusion/maintenance overhead.

Copilot · 2026-03-23T21:59:27Z

confidential-assets/tests/units/api/negativeTransfer.test.ts

  const coinType = "0x1::aptos_coin::AptosCoin";
  const tokenAddress = "0x000000000000000000000000000000000000000000000000000000000000000a";
-  const fundAmount = 1 * 10 ** 8;
+  const fundAmount = 10 * 10 ** 8;
  const depositAmount = 0.5 * 10 ** 8;
  const recipientAccAddr = "0x82094619a5e8621f2bf9e6479a62ed694dca9b8fd69b0383fce359a3070aa0d4";
  const transferAmount = BigInt(0.1 * 10 ** 8);


Near this setup block, the test logs alice.privateKey/decryption keys to stdout (a few lines below). In CI these end up in build logs, which is sensitive even for test accounts and makes it easy to accidentally leak real keys if the helper setup changes. Please remove those logs or gate them behind an explicit debug env flag.

Copilot · 2026-03-23T21:59:28Z

confidential-assets/tests/units/api/negativeWithdraw.test.ts

  const coinType = "0x1::aptos_coin::AptosCoin";
  const tokenAddress = "0x000000000000000000000000000000000000000000000000000000000000000a";
-  const fundAmount = 1 * 10 ** 8;
+  const fundAmount = 10 * 10 ** 8;
  const depositAmount = 0.5 * 10 ** 8;
  const withdrawAmount = BigInt(0.1 * 10 ** 8);


Near this setup block, the test logs alice.privateKey/decryption keys to stdout (a few lines below). In CI these end up in build logs, which is sensitive even for test accounts and makes it easy to accidentally leak real keys if the helper setup changes. Please remove those logs or gate them behind an explicit debug env flag.

…anup - Skip Playwright browser download in confidential-assets CI job (PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1) since it only runs confidential tests, not browser tests - Remove ./confidential-assets from lint:all/check:all/fmt:all turbo filters since that package has no lint/check/fmt scripts - Remove private key and decryption key console.log statements from negativeTransfer, negativeWithdraw, and negativeNormalize test files to avoid leaking keys in CI logs - Clean up unused imports (numberToBytesLE, bytesToNumberLE, bytesToHex, ed25519modN) that were only needed for the removed key logging Co-authored-by: Greg Nazario <greg@gnazar.io>

gregnazario requested a review from Copilot March 21, 2026 05:10

Copilot started reviewing on behalf of gregnazario March 21, 2026 05:11 View session

Copilot AI reviewed Mar 21, 2026

View reviewed changes

gregnazario marked this pull request as ready for review March 21, 2026 05:36

gregnazario requested a review from a team as a code owner March 21, 2026 05:36

gregnazario requested a review from Copilot March 21, 2026 05:36

Copilot started reviewing on behalf of gregnazario March 21, 2026 05:36 View session

Copilot AI reviewed Mar 21, 2026

View reviewed changes

cursoragent and others added 7 commits March 23, 2026 17:24

Move @aptos-labs/ts-sdk to dependencies in gas-station

8919f0a

The SDK is imported at runtime in server.ts and client.ts, so it belongs in dependencies rather than devDependencies to avoid breaking production installs that omit devDependencies. Co-authored-by: Greg Nazario <greg@gnazar.io>

Remove redundant peerDependencies from gas-station

c296abc

gas-station is a demo app, not a published library. The SDK is already in dependencies via workspace:*, so the peerDependencies entry is unnecessary and would only trigger warnings. Co-authored-by: Greg Nazario <greg@gnazar.io>

gregnazario force-pushed the cursor/turborepo-monorepo-structure-2bbb branch from 169dcaa to c296abc Compare March 23, 2026 21:24

gregnazario requested a review from Copilot March 23, 2026 21:24

Copilot started reviewing on behalf of gregnazario March 23, 2026 21:25 View session

Copilot AI reviewed Mar 23, 2026

View reviewed changes

gregnazario requested a review from Copilot March 23, 2026 21:54

Copilot started reviewing on behalf of gregnazario March 23, 2026 21:55 View session

Copilot AI reviewed Mar 23, 2026

View reviewed changes

	"@aptos-labs/ts-sdk": "workspace:*"
	"@aptos-labs/ts-sdk": "link:../.."

	"@aptos-labs/ts-sdk": "workspace:*",
	"@aptos-labs/ts-sdk": "link:../..",

	"@aptos-labs/ts-sdk": "workspace:*"
	"@aptos-labs/ts-sdk": "file:../.."

Conversation

gregnazario commented Mar 21, 2026 • edited by cursor bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Test Plan

Review feedback addressed

Related Links

Checklist

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

gregnazario commented Mar 21, 2026 •

edited by cursor bot

Loading